docs: normalize remaining project naming in legacy docs#159
Merged
Conversation
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Code Review
This pull request standardizes the project name spelling to 'CompText V7' across the documentation files. A review comment suggests improving the readability of a comparison table in 'docs/research_positioning.md' by removing redundant project name repetitions in the boundary column, as the name is already defined in the header.
Comment on lines
+61
to
+65
| | RAG evaluation | Retrieval quality, answer grounding, citation coverage, or generated-answer quality. | CompText V7 does not retrieve documents or judge generated answers. It checks whether fixture-defined operational state survives compact/replay cycles. | | ||
| | Vector memory | Embedding-based recall and similarity search over stored memories. | CompText V7 does not use embeddings or vector databases. It compares explicit fixture IDs, fields, attachments, and normalized values. | | ||
| | KV-cache compression | Serving-layer efficiency for model attention/cache reuse. | CompText V7 does not optimize model internals or inference caches. It emits reviewable replay artifacts and field-survival metrics. | | ||
| | Workflow orchestration | Durable execution, retries, scheduling, state machines, and tool execution. | CompText V7 does not run autonomous workflows. It validates whether replayed operational state still contains fixture-defined continuation requirements. | | ||
| | Learned context compression | Model-learned summaries or compressed prompts optimized for downstream performance. | CompText V7 does not train or evaluate a learned compressor. It measures deterministic replay preservation under controlled fixtures. | |
Contributor
There was a problem hiding this comment.
The repetition of the project name in every cell of this column is redundant since it is already specified in the column header. Removing it would improve readability and align with the style used in other tables and lists in the documentation (e.g., the 'Not claimed' section on line 83 and the 'Stable API routes' table in docs/API_SURFACE.md).
Suggested change
| | RAG evaluation | Retrieval quality, answer grounding, citation coverage, or generated-answer quality. | CompText V7 does not retrieve documents or judge generated answers. It checks whether fixture-defined operational state survives compact/replay cycles. | | |
| | Vector memory | Embedding-based recall and similarity search over stored memories. | CompText V7 does not use embeddings or vector databases. It compares explicit fixture IDs, fields, attachments, and normalized values. | | |
| | KV-cache compression | Serving-layer efficiency for model attention/cache reuse. | CompText V7 does not optimize model internals or inference caches. It emits reviewable replay artifacts and field-survival metrics. | | |
| | Workflow orchestration | Durable execution, retries, scheduling, state machines, and tool execution. | CompText V7 does not run autonomous workflows. It validates whether replayed operational state still contains fixture-defined continuation requirements. | | |
| | Learned context compression | Model-learned summaries or compressed prompts optimized for downstream performance. | CompText V7 does not train or evaluate a learned compressor. It measures deterministic replay preservation under controlled fixtures. | | |
| | RAG evaluation | Retrieval quality, answer grounding, citation coverage, or generated-answer quality. | Does not retrieve documents or judge generated answers. It checks whether fixture-defined operational state survives compact/replay cycles. | | |
| | Vector memory | Embedding-based recall and similarity search over stored memories. | Does not use embeddings or vector databases. It compares explicit fixture IDs, fields, attachments, and normalized values. | | |
| | KV-cache compression | Serving-layer efficiency for model attention/cache reuse. | Does not optimize model internals or inference caches. It emits reviewable replay artifacts and field-survival metrics. | | |
| | Workflow orchestration | Durable execution, retries, scheduling, state machines, and tool execution. | Does not run autonomous workflows. It validates whether replayed operational state still contains fixture-defined continuation requirements. | | |
| | Learned context compression | Model-learned summaries or compressed prompts optimized for downstream performance. | Does not train or evaluate a learned compressor. It measures deterministic replay preservation under controlled fixtures. | |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary:
docs/API_SURFACE.mdanddocs/research_positioning.mdtoCompText V7.Changed files:
docs/API_SURFACE.mddocs/research_positioning.mdScope:
Non-goals confirmed:
Testing: